-
-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent iOS host object installation from getting the wrong bridge #2146
Prevent iOS host object installation from getting the wrong bridge #2146
Conversation
Hey @gabrieldonadel, thanks for noticing this and taking your time to fix this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, I made a PR changing it some time ago: #2120 but it is stuck with some problems in core. I think we can merge that one to fix at least one of the issues already 🚀
…oftware-mansion#2146) Similar to software-mansion/react-native-reanimated#5953, using `[RCTBridge currentBridge]` may lead to the wrong bridge in apps that have multiple React instances, as is the case for expo-dev-client. This results in apps sometimes crashing when reloading the bundle after interacting with the DevMenu.
Description
Similar to software-mansion/react-native-reanimated#5953, using
[RCTBridge currentBridge]
may lead to the wrong bridge in apps that have multiple React instances, as is the case for expo-dev-client. This results in apps sometimes crashing when reloading the bundle after interacting with the DevMenu.Changes
Instead of using
[RCTBridge currentBridge]
we can just callself.bridge
and ensure the correct bridge is always used